The change obviously suits me but it could be indeed worth it to discuss it with Alex (author of DrawMesh) and Erik (for topologies)
For consistency, I would at least to the same for triangles and Tetrahedron, as suggested 👍

I would advocate going for the third option when no facet is available in the topology. And it would only be slower for the first timestep.

I would advocate going for the third option when no facet is available in the topology. And it would only be slower for the first timestep.

The problem with that solution is that:

• we need to store the generated quads
• we will still need to keep track of the hexas' state in case of a topology change (removal of an hexa for example)
• will quite change the "spirit" of this class

So in this case, the best would be that the topology itself manages the quad (the problem in the first place actually) with a function like BaseMeshTopology::generateSubElements<Hexa,Quad> or something like that.

Finally my preferred solution actually would be simply to call drawHexahedra() instead of drawQuads from the DrawTool, which is taking care of creating the visual quads itself. But maybe @alxbilger had a reason to not call it.